From ec147ba6fa6277feb5d485bd2366f255ab06d6cf Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 10 Jan 2009 12:49:58 +0000 Subject: [PATCH] (Decoding Output): Document that null bytes force no-conversion for reading process output. --- doc/lispref/processes.texi | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi index 265e63b6dee..ae3246f0d29 100644 --- a/doc/lispref/processes.texi +++ b/doc/lispref/processes.texi @@ -1388,7 +1388,10 @@ converts the unibyte output to multibyte using system to use (@pxref{Process Information}). Otherwise, the coding system comes from @code{coding-system-for-read}, if that is non-@code{nil}; or else from the defaulting mechanism (@pxref{Default -Coding Systems}). +Coding Systems}). If the text output by a process contains null +bytes, Emacs by default uses @code{no-conversion} for it; see +@ref{Lisp and Coding Systems, inhibit-null-byte-detection}, for how to +control this behavior. @strong{Warning:} Coding systems such as @code{undecided} which determine the coding system from the data do not work entirely -- 2.30.2